Skip to main content

DINA—Development of open source and open services for natural history collections & research

Bookreader Item Preview

texts

DINA—Development of open source and open services for natural history collections & research

by
Glöckler, Falko; Macklin, James; Shorthouse, David; Bölling, Christian; Bilkhu, Satpal; Gendreau, Christian

Publication date
Usage
Attribution 4.0 InternationalCreative Commons Licenseby
Topics
collection data management, research data, software development, collaboration, interoperability
Publisher
Pensoft Publishers
Collection
biodiversity
Contributor
Pensoft Publishers
Language
English
Rights
https://biodiversitylibrary.org/permissions
Rights-holder
Copyright held by individual article author(s).
Volume
4
Item Size
2.9M
Abstract
The DINA Consortium (DINA = “DIgital information system for NAtural history data”, https://dina-project.net) is a framework for like-minded practitioners of natural history collections to collaborate on the development of distributed, open source software that empowers and sustains collections management. Target collections include zoology, botany, mycology, geology, paleontology, and living collections. The DINA software will also permit the compilation of biodiversity inventories and will robustly support both observation and molecular data.
The DINA Consortium focuses on an open source software philosophy and on community-driven open development. Contributors share their development resources and expertise for the benefit of all participants. The DINA System is explicitly designed as a loosely coupled set of web-enabled modules. At its core, this modular ecosystem includes strict guidelines for the structure of Web application programming interfaces (APIs), which guarantees the interoperability of all components (https://github.com/DINA-Web). Important to the DINA philosophy is that users (e.g., collection managers, curators) be actively engaged in an agile development process. This ensures that the product is pleasing for everyday use, includes efficient yet flexible workflows, and implements best practices in specimen data capture and management.
There are three options for developing a DINA module:



create a new module compliant with the specifications (Fig. 1),


modify an existing code-base to attain compliance (Fig. 2), or


wrap a compliant API around existing code that cannot be or may not be modified (e.g., infeasible, dependencies on other systems, closed code) (Fig. 3).



create a new module compliant with the specifications (Fig. 1),
modify an existing code-base to attain compliance (Fig. 2), or
wrap a compliant API around existing code that cannot be or may not be modified (e.g., infeasible, dependencies on other systems, closed code) (Fig. 3).
All three of these scenarios have been applied in the modules recently developed: a module for molecular data (SeqDB), modules for multimedia, documents and agents data and a service module for printing labels and reports:
The SeqDB collection management and molecular tracking system (Bilkhu et al. 2017) has evolved through two of these scenarios. Originally, the required architectural changes were going to be added into the codebase, but after some time, the development team recognised that the technical debt inherent in the project wasn’t worth the effort of modification and refactoring. Instead a new codebase was created bringing forward the best parts of the system oriented around the molecular data model for Sanger Sequencing and Next Generation Sequencing (NGS) workflows.
In the case of the Multimedia and Document Store module and the Agents module, a brand new codebase was established whose technology choices were aligned with the DINA vision. These two modules have been created from fundamental use cases for collection management and digitization workflows and will continue to evolve as more modules come online and broaden their scope.
The DINA Labels & Reporting module is a generic service for transforming data in arbitrary printable layouts based on customizable templates. In order to use the module in combination with data managed in collection management software Specify (http://specifysoftware.org) for printing labels of collection objects, we wrapped the Specify 7 API with a DINA-compliant API layer called the “DINA Specify Broker”. This allows for using the easy-to-use web-based template engine within the DINA Labels & Reports module without changing Specify’s codebase.
In our presentation we will explain the DINA development philosophy and will outline benefits for different stakeholders who directly or indirectly use collections data and related research data in their daily workflows. We will also highlight opportunities for joining the DINA Consortium and how to best engage with members of DINA who share their expertise in natural science, biodiversity informatics and geoinformatics.
Addeddate
2025-06-09 22:03:20
Bhl_virtual_titleid
210882
Bhl_virtual_volume
v.4 (2020)
Call number
10_3897_biss_4_59070
Call-number
10_3897_biss_4_59070
Foldoutcount
0
Genre
article
Identifier
dinadevelopment4gloc
Identifier-ark
ark:/13960/s29hgk896fm
Identifier-bib
10_3897_biss_4_59070
Identifier-doi
10.3897/biss.4.59070


comment
Reviews

78 Views

DOWNLOAD OPTIONS

download 1 file
B/W PDF download
download 1 file
CHOCR download
DAISY

For users with print-disabilities

EPUB
download 1 file
FULL TEXT download
download 1 file
HOCR download
download 1 file
ITEM TILE download
download 1 file
OCR PAGE INDEX download
download 1 file
OCR SEARCH TEXT download
download 1 file
PAGE NUMBERS JSON download
download 1 file
PDF download
download 1 file
SINGLE PAGE PROCESSED JP2 ZIP download
download 1 file
TORRENT download
download 17 Files
download 8 Original
SHOW ALL

IN COLLECTIONS

Biodiversity Heritage Library

Uploaded by Smithsonian Libraries and Archives on

SIMILAR ITEMS (based on metadata)

Terms of Service (last updated 12/31/2014)